Hello.

I have a some problems with Hyper-V on Win8 x64. After I install Hyper-V my microphone stopped work. If I uninstall Hyper-V efficiency of microphone is restored.

In my other OS (Win7 and WinXp) microphone work normally in any case. All the settings of microphone is OK. I don`t change anything. But after installing Hyper-V instead of my voice can hear only the hiss. Connecting the microphone to a different port has no effect.

Can anybody help me with this problem?

Sorry, forgot.

"I noticed it the first time with the Microsoft sound drivers installed. I then installed the VIA drivers in the hope to solve it, but after a test (with the sound recorder software of Windows) the problem still existed". I did the same, only my sound card is Realtek ALC892.

And just in case the configuration:

ASRock 880GXH/USB3 - Realtek ALC892

AMD Athlon II X4 640

Hynix PC3-10600 DDR3 SDRAM 2x2Gb

Seagate ST32000542AS

Inwin 600W

Microphone Gembird M-04

Win8 Enterprise

Hello,

I can confirm this problem. Sound in general works fine (with or without Hyper-V enabled).

The microphone itself produces only static. No matter which port it is plugged into. It is definitely connected to the Hyper-V role of Windows 8. It worked under Windows 7 and it works under Windows 8, but only if the Hyper-V role is deactivated. This problem has been already mentioned in this post:

http://social.technet.microsoft.com/Forums/en-US/w8itprohardware/thread/aeab61e0-745d-46b9-84c6-c784e14ecb88?prof=required

One solution which worked in the post too, was to disable Hyper-V.

It seems to be unrelated to the used drivers. I noticed it the first time with the Microsoft sound drivers installed. I then installed the VIA drivers in the hope to solve it, but after a test (with the sound recorder software of Windows) the problem still existed. The static is present throughout various programs, e.g. Teamspeak or sound recorder. I tested two different microphones, still the same problem. No voice is audible, just static.

Since it is probably related to the hardware, I'll give my specs

• Windows 8 64-bit
• ASUS M4A785TD-V Evo Mainboard with an AMD 785 Chipset
• Integrated VIA VT1708S Soundchip with 10.005D drivers (dated 25-July-2012, latest available up to date of post)

If there is more information which I can help to provide, please feel free to ask.

Kind Regards

The management OS - the OS that you log on to at the physical console should always have access to the physical devices such as the microphone.

Virtual machines would not have access to these devices, such as the physical microphone.  If you are using a VMConnect (Hyper-V VM Console) window and you expect the VM to have access to the microphone - it won't.

If you boot directly to the same VHD (VHD boot on the hardware) then the OS in the VHD will have access to the hardware as there is no hypervisor involved.

This is what raises the questions, there are lots of ways to roll this.

If all you did was add the Hyper-V Role, then fundamentally nothing changed for that particular OS and if the audio device configuration was not modified, it should still work as it did.

All You wrote is right. But

- I don`t expect the VM to have access to the microphone. I need the microphone in my Win8 OS

- I using Hyper-V VM Console to run my VM, respectively I don`t boot directly from VHD on my hardware

- All I did was add the Hyper-V Role, then absolutely nothing changed for that particular OS and the audio device configuration was not modified... microphone don`t work.

And microphone break after I simply install such component us Hyper-V. I don`t even need to configure Hyper-V or add any VM - only install such component us Hyper-V and microphone don`t work (just checked).

Stopping "Manage virtual machine Hyper-V" service not solve the problem.

I will try to continue.

Is your microphone USB? Or plugged into the sound card via a headphone plug?

The microphone is attached directly into the plug of the mainboard (onboard soundcard). No usb or discrete soundcard is used. At least in my case. And I can confirm the statement of slava_oz. The microphone doesn't work in the host, i.e. Windows 8 Pro 64-bit. The VM isn't even active.

I can even confirm the problem that I can hear my voice in the speakers, I think I tested this with Teamspeak. But as soon as I record it, I can only hear static.

It is just the Hyper-V role. As soon as it's active the microphone produces only static.

The microphones used are:

• Speedlink Medusa NX Stereo Headset
• Zalman ZM-MIC1

Kind regards

Is your microphone USB? Or plugged into the sound card via a headphone plug?

Into the sound card via a headphone plug

Hi ,

I enable Hyper-v on my Windows 8 X64 enterprise laptop. I can use the Micrsophone. Did you test if you plug a headphone, does it work? 

Please also update the latest realtek driver from their website. Thanks. 

I solved the problem. It was included in the BIOS options  "Secure Virtual Machine". Turn Disable and microphone work fine. And now I don`t understand whose fault: AMD or Microsoft?

Hi ,

I enable Hyper-v on my Windows 8 X64 enterprise laptop. I can use the Micrsophone. Did you test if you plug a headphone, does it work? 

Please also update the latest realtek driver from their website. Thanks.

A BIOS setting is a hardware issue not the fault of the system that is enforcing, obeying, or applying the BIOS setting.

It is probably less fault, than a poorly documented and therefore understood setting - also relatively new.  Possibly implemented (default on) before its implications are fully understood.

Lets back up to architecture a bit.

Adding Hyper-V containerizes the installed operating system into a special VM Microsoft calls the management OS.  (XenServer calls it dom0 (domain0)).  This is technically a VM, like all other VMs but it is privileged and has a special channel to the hypervisor that is below it and the layer now directly touching the hardware.

As virtualization features have been moving to the hardware level, various settings move to the BIOS.  And it is the job of the hypervisor to implement whatever the setting is.  Or possibly, not have access to something based on the BIOS setting causing the hardware to block it and not expose it to the system.

A BIOS setting is a hardware issue not the fault of the system that is enforcing, obeying, or applying the BIOS setting.

It is probably less fault, than a poorly documented and therefore understood setting - also relatively new.  Possibly implemented (default on) before its implications are fully understood.

Lets back up to architecture a bit.

Adding Hyper-V containerizes the installed operating system into a special VM Microsoft calls the management OS.  (XenServer calls it dom0 (domain0)).  This is technically a VM, like all other VMs but it is privileged and has a special channel to the hypervisor that is below it and the layer now directly touching the hardware.

As virtualization features have been moving to the hardware level, various settings move to the BIOS.  And it is the job of the hypervisor to implement whatever the setting is.  Or possibly, not have access to something based on the BIOS setting causing the hardware to block it and not expose it to the system.

After reading the post I too disabled the "Secure Virtual Machine Mode" (SVM). This should be AMD's virtualization mode (AMD-V) the counterpart to Intel's Virtualization Mode (Intel VT), right?.

The Problem is only that after SVM has been deactivated, I can install the Hyper-V Management Tools but not the Hyper-V Platform. In the Windows feature menu it tells me 'Hyper-V cannot be installed. Virtualization support is disabled in the Firmware'. Probably because I have 64-bit Version of Windows, and this feature is needed. Of course the micrphone works :)

I don't think that AMD or Microsoft are to blame. I believe that the either the mainboard or the BIOS developer have done some mistake. Problem is that Hyper-V has been introduced with Windows 8 to the mass market. And so the normal consumer mainboards have never been tested with this feature.

So it seems to be a BIOS problem (AMI BIOS by the way). Since I already have the latest BIOS version, there seems to be no solution for me as long as I stick to my Motherboard. Or probably by buying a separate sound card, where the BIOS cannot interfere on the same level as with the onboard sound.

Regards

After reading the post I too disabled the "Secure Virtual Machine Mode" (SVM). This should be AMD's virtualization mode (AMD-V) the counterpart to Intel's Virtualization Mode (Intel VT), right?.

The Problem is only that after SVM has been deactivated, I can install the Hyper-V Management Tools but not the Hyper-V Platform. In the Windows feature menu it tells me 'Hyper-V cannot be installed. Virtualization support is disabled in the Firmware'. Probably because I have 64-bit Version of Windows, and this feature is needed. Of course the micrphone works :)

I don't think that AMD or Microsoft are to blame. I believe that the either the mainboard or the BIOS developer have done some mistake. Problem is that Hyper-V has been introduced with Windows 8 to the mass market. And so the normal consumer mainboards have never been tested with this feature.

So it seems to be a BIOS problem (AMI BIOS by the way). Since I already have the latest BIOS version, there seems to be no solution for me as long as I stick to my Motherboard. Or probably by buying a separate sound card, where the BIOS cannot interfere on the same level as with the onboard sound.

Regards

I disabled the SVM without uninstalling Hyper-V. After reboot it`s work fine. In "Enable or disable Windows component" on item Hyper-V all checkboxes are enabled and marked.

Maybe You need enable SVM, install Hyper-V and after that disable SVM? Or I not correct understood You?

And maybe You right and this is a problem of motherboards developers, that don`t want to adapt capabilities of CPU to capabilities of new OS.

By the way my BIOS is also from AMI.

Hardware virtualization is required for Hyper-V. 

Is there a new BIOS from Asus Asrock available for your MB?

Hardware virtualization is required for Hyper-V. 

Is there a new BIOS from Asus available for your MB?

Hi,

I think that I have already the latest BIOS installed. However I'm going to check that and try to (re)flash it with the latest version.

Kind regards

Hardware virtualization is required for Hyper-V. 

Is there a new BIOS from Asus Asrock available for your MB?

I checked my Asus M4A785TD-M EVO board which has the AMD 785G/SB710 chipset and the microphone does work.

So, it's likely just a BIOS issue with the ASrock board.

I checked my Asus M4A785TD-M EVO board which has the AMD 785G/SB710 chipset and the microphone does work.

So, it's likely just a BIOS issue with the ASrock board.

 

I checked my Asus M4A785TD-M EVO board which has the AMD 785G/SB710 chipset and the microphone does work.

So, it's likely just a BIOS issue with the ASrock board.

 

 This problem is not only Asrock motherboard. See Wincling post. Who is Your BIOS manufacter?

I've just checked the mainboard specs of the ASUS '-M' board. It has a BIOS from AMI. The board is nearly identical to my '-V' board. It's even the same soundchip. One of the differences I can recognize is, that is has more expansion slots. 

So I think that this confirms, that it is 'just' a BIOS issue. 

Tomorrow when I have a bit of time I'm going to try the update to see if this issue can be resolved.

I checked my Asus M4A785TD-M EVO board which has the AMD 785G/SB710 chipset and the microphone does work.

So, it's likely just a BIOS issue with the ASrock board.

 

 This problem is not only Asrock motherboard. See Wincling post. Who is Your BIOS manufacter?

I've just checked the mainboard specs of the ASUS '-M' board. It has a BIOS from AMI. The board is nearly identical to my '-V' board. It's even the same soundchip. One of the differences I can recognize is, that is has more expansion slots. 

So I think that this confirms, that it is 'just' a BIOS issue. 

Tomorrow when I have a bit of time I'm going to try the update to see if this issue can be resolved.

You wrote that You already have the latest BIOS.

If this is a BIOS trouble why the same virtualization technology perfectly work on my hardware in all others Microsoft OS (WinXP x32 and Win8 x64)? Hardware implementation identical for all OS, but OS have various virtualization layers. I think problem in OS.

It's a BIOS implementation issue. 

Virtualization has always been hard for vendors. There are numerous Gigabyte boards with USB3 that have Hyper-V issues, but not all.  Toshiba had issues with virtualization on some of their laptops, but not all.  It took them 3 different versions of the BIOS for the M400 to get it right.

Every implementation of a virtualization layer is different. 

The "latest" BIOS doesn't mean it was created after Windows 8 was released and also it may have never been tested with Windows 8.  For example, on your ASRock MB, the last BIOS update was 2010.  ASRock needs to update the BIOS for Windows 8.

You could try disabling USB3, that's made a difference in some cases.

Wincling, I have the 2104 version ( I had to update to this version for Win8+Hyper-V to boot correctly), it's odd that it's missing on your board, and you have the same 2103 and newer 2105.

It's a BIOS implementation issue. 

Virtualization has always been hard for vendors. There are numerous Gigabyte boards with USB3 that have Hyper-V issues, but not all.  Toshiba had issues with virtualization on some of their laptops, but not all.  It took them 3 different versions of the BIOS for the M400 to get it right.

Every implementation of a virtualization layer is different. 

The "latest" BIOS doesn't mean it was created after Windows 8 was released and also it may have never been tested with Windows 8.  For example, on your ASRock MB, the last BIOS update was 2010.  ASRock needs to update the BIOS for Windows 8.

You could try disabling USB3, that's made a difference in some cases.

Wincling, I have the 2104 version ( I had to update to this version for Win8+Hyper-V to boot correctly), it's odd that it's missing on your board, and you have the same 2103 and newer 2105.

Try disabling USB3 in your bios and see if that makes any difference.

Also, do you have a USB microphone you could try?

It's a BIOS implementation issue. 

Virtualization has always been hard for vendors. There are numerous Gigabyte boards with USB3 that have Hyper-V issues, but not all.  Toshiba had issues with virtualization on some of their laptops, but not all.  It took them 3 different versions of the BIOS for the M400 to get it right.

Every implementation of a virtualization layer is different. 

The "latest" BIOS doesn't mean it was created after Windows 8 was released and also it may have never been tested with Windows 8.  For example, on your ASRock MB, the last BIOS update was 2010.  ASRock needs to update the BIOS for Windows 8.

You could try disabling USB3, that's made a difference in some cases.

Wincling, I have the 2104 version ( I had to update to this version for Win8+Hyper-V to boot correctly), it's odd that it's missing on your board, and you have the same 2103 and newer 2105.

I know that Asrock BIOS is old. But it hardly updated. I wrote about my problem to Asrock already. But the updates or answer, probably not worth expect.

I have rechecked the version of my BIOS and I can confirm that I have already the latest version installed (2105). Which makes it really odd, since it works on the nearly equal '-M' board, like you have Steve.

I'm going to try the same thing you did slava_oz, and write to the ASUS support. But since the board is already a bit older, I don't think that there will be any reaction.

That's a bit sad since Hyper-V is a really useful feature for me, one of the reasons why I have switched to Windows 8.

It seems that I have used all the possibilities which I can think of. Well, there is on thing left, if ASUS doesn't react, I'll probably get a separate sound card and try it that way.

Best wishes

Try disabling USB3 in your bios and see if that makes any difference.

Also, do you have a USB microphone you could try?

Didn't think so, that's more of a solution for when the BIOS isn't allow Hyper-V to boot.  But, it was worth a shot.

With some Gigabyte mbs, Hyper-V won't work at all.

Were you able to try a USB microphone?

With some Gigabyte mbs, Hyper-V won't work at all.

Were you able to try a USB microphone?

I have got answer from Asrock.

Thanks for contacting ASRock.

We did the
test with similar configuration, but cannot see
the symptom.
With Hyper-V function,
the microphone works fine and can record a message via windows 8's
built in recorder.
Please remove the power cord from MB, and use jumper to clear
CMOS and load BIOS default for try.
You can refer the manual
http://download.asrock.com/manual/880GXHUSB3.pdf page 11 and
23.
Please connect the mic to the front panel and change another MIC to
verify.

Experiencing the same issue.  Tried everything, but cannot get mic to work with Hyper-V enabled.  The only way I can use the mic - Skype, in particular, is to turn off Hyper-V.

AMD Phenom II

ASUS M4A77TD motherboard with onboard audio (VIA chipset, latest drivers installed.)

Windows 8 64 bit

Did you do a cold reset?

Do you mean resetting my MB/BIOS with jumpers 'n stuff?

I turn off virtualization in my bios and microphone works. Turn it on and it does not work.

Wish I could fix as I use hyper v and have to have virtualization turned on in Windows 8.

I don't have a Secure Virtualization Machine Option in my BIOS. Is there another fix for this???

Hi,

I also have exact same configuration in my PC, I installed the latest BIOS update from ASUS website

http://support.asus.com/Download.aspx?SLanguage=en&m=M4A77TD&p=1&s=24

It has "Secure Virtualization Machine" options under CPU Configuration in BIOS

just disable it, and the mic should work. I know it is not a permanent solutions but at least it is something.

Well, it's not all systems. 

I just checked the microphone on one of my Win8 systems with Hyper-V enabled and installed and it works.  It's an Asus M4A785TD-M EVO.

Microphone also works on my Surface Pro with Hyper-V enabled and installed.

Confirmed.  The singal from any of my audio chipset's ports turns to pure buzzing when hyper-v is installed.  Uninstalling hyper-v restores a clean signal from the audio chipset.

Motherboard: GA-880GMA-USB3

The funny thing is that the realtek drivers for this board seem to read the signal just fine.  That is, if you use the realtek control panel to listen to the device there is no buzzing.  The problem is definitely somewhere between the drivers and the input device that programs get from windows.  In fact, simply clicking "listen to this device" in the windows recording properties gets the buzzing going.

Hello, i have the same problem on my configuration:

- Windows 8 Pro 64

- Gigabyte 990XA - UD3 rev.1   |   latest BIOS - f13 (also tested on f14b  - the same problem occurs)

...still no good fix since December.

Kind Regards.

I received word from the hardware manufacturer and they wrote this board is not Win 8 supported. A fix will not be released.

I received word from the hardware manufacturer and they wrote this board is not Win 8 supported. A fix will not be released.

You did not solve the problem you are working around the issue by using a different device that is USB that contains a microphone. This issue also does not occur if you use a USB headset it is only showing up if you use the 3.5mm microphone jack.

You did not solve the problem you are working around the issue by using a different device that is USB that contains a microphone. This issue also does not occur if you use a USB headset it is only showing up if you use the 3.5mm microphone jack.